Transferring records between tables using a change transaction log

ABSTRACT

A method and apparatus for transferring records between database tables using a transaction log. In one embodiment of the method, a first application generates a transaction for deleting a record from a first table in a database. In response to the generation of the first transaction, a copy of the record is stored in an entry of a transaction log before the record is deleted from the first table. A second application generates an instruction for copying the record from the transaction log to a second table, and the record is copied from the entry to the second table.

BACKGROUND

A search engine is an information retrieval system that is designed to help users find information. Search engines help to minimize the time required to find information of interest and the amount of information which must be consulted. The most popular form of search engine is a Web search engine that searches for information on the public World Wide Web. Other kinds of search engines include enterprise search engines, which can search for information stored in, for example, records in one or more databases on an intranet.

Search engines provide a search interface for users to specify search criteria. Search engines identify data objects (e.g., documents, database records, etc.) that contain information that match the specified search criteria. Word searching is the most popular form of search, and a search match occurs when a data object contains a word or words that are specified in a user query. The method or apparatus will be described with reference to word searching, it being understood that the claims below should not be limited thereto.

There are several varieties of syntax in which a search engine user can express a query. Some methods are formalized and require a strict, logical and algebraic syntax. The query can be quite simple, a single word at minimum. Building a more complex query may require the use of Boolean operators (e.g., AND, OR, NOT, etc.) that allow a user to refine and extend the terms of the search. Other approaches are less strict and allow for a less defined query.

SUMMARY

A method and apparatus for transferring records between database tables using a transaction log. In one embodiment of the method, a first application generates a transaction for deleting a record from a first table in a database. In response to the generation of the first transaction, a copy of the record is stored in an entry of a transaction log before the record is deleted from the first table. A second application generates an instruction for copying the record from the transaction log to a second table, and the record is copied from the entry to the second table.

BRIEF DESCRIPTION OF THE DRAWINGS

The example embodiments may be better understood, and its numerous objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings.

FIG. 1 is a simplified block diagram of a data processing system.

FIG. 2 is a graphical representation of an example search index.

FIG. 3 is a flow chart illustrating relevant aspects of an example process implemented by the transaction monitor of FIG. 1.

FIG. 4 is a graphical representation showing relevant aspects of an example transaction log employed in the system of FIG. 1.

FIG. 5 illustrates relevant operational aspects of an example process that is implemented by the transaction monitor of FIG. 1.

FIG. 6 illustrates relevant aspects of an example process that is performed by the index update module of FIG. 1.

DETAILED DESCRIPTION

Search engines typically use one or more search indexes to quickly locate data objects that match search criteria (i.e., contain words specified in a search query). Without a search index, the search engine may need to scan every data object in a corpus, which would take a considerable amount of time and computing power, in order to find data objects whose contents match the search criteria. Using a search index, for example, 10,000 data objects can be queried for specified words within milliseconds, whereas a sequential scan of every word in the data objects, could take hours, especially if the data objects are large. No search engine user would be comfortable waiting several hours to get search results. The trade off for the time saved during information retrieval is that additional computer storage is required to store the search index, and that it takes time for the search engine to create and update the search index. In some instances, users cannot submit a search query while the search engine is creating or updating a search index.

Search indexes vary in architecture to meet various design factors such as the amount of memory needed to store the index, how to store the index data (e.g., whether index information should be data compressed), etc. In general, search indexes contain entries, each of which maps a keyword to one or more identifiers that identify respective data objects that contain one or more instances of the keyword. Search indexes may include additional information such as the frequency (i.e., the number of instances) of each keyword in the data objects or the positions of the keyword in data objects.

Search engines use search indexes to identify one or more data objects that contain one or more keywords that are identified in a search query. Once identified, the search engine can sort the identified data objects according to relevance using, for example, keyword position and/or keyword frequency information mentioned above. The sorted data objects are then presented to the user in a search results list. Placing the most relevant data objects first in the search result list, along with content snippets thereof, reduces the time required by users to determine whether one or more of the identified data objects are relevant.

The initial creation of a search index is a process well understood by those of ordinary skill in the art. Once created, search indexes should be updated to reflect changes (i.e., deletions, modifications, or new insertions) of data objects in the corpus. If search indexes are not updated, search engines that use the index may generate search result lists that are less than accurate. For example, suppose a data object is deleted from the corpus after the search index is first created. If the search index is not updated, the search index will inaccurately map one or more keywords that were contained in the deleted data object to the data object's identifier. Further suppose the search engine receives a query from a user that specifies a keyword that was contained in the deleted data object. In response to receiving the query, the search engine will access the search index using the specified keyword, identify the deleted data object as containing the keyword, and generate a search result list that contains the deleted data object. Only when the user attempts to access the data object after seeing the results list, will the user learn that the data object has been deleted.

Search indexes should be updated so that they accurately reflect changes to a corpus of data objects. In other words, search indexes should be updated soon after data objects have been deleted, modified or newly inserted. An apparatus or method for updating a search index is described below. The method or apparatus can be implemented as one or more computer programs executing on one or more processors of one or more computer systems, although those skilled in the art will readily recognize that the equivalent of such software may also be constructed in hardware or a combination of hardware and software. If the method of apparatus is implemented as a computer program, the program may be stored on one or more conventional computer readable mediums that may include, for example: magnetic storage media such as a magnetic disk (e.g., a disk drive); optical storage media such as an optical disk; solid state electronic storage devices such as random access memory (RAM), or read only memory (ROM); or any other device or medium employed to store computer program instructions.

A transaction monitor is described below for detecting transactions that modify or delete existing data objects of a corpus, or change transactions that insert new data objects into the corpus. For purposes of explanation only, the term modification is defined to include overwriting data within an existing data object with new data, removing some of the data without replacing it, or appending new data to an existing data object. In one embodiment, the transaction monitor, either before or after a data object is modified, deleted, or inserted in accordance with a corresponding change transaction, generates and sends an update index message to a search engine that has access to a search index that is associated with the corpus of data objects. This update index message may include information unique to the corresponding change transaction. For example, if the change transaction is configured for deleting a first data object, the corresponding update index message that is generated by the monitor may include an identifier of the first data object or information which can be used to generate the identifier of the first data object. Additionally, the update index message may include an indication that the first data object was or will be deleted, although the indication can merely indicate that a data object is being removed.

Update index messages can also be generated in response to the transaction monitor detecting a transaction to modify an existing data object or a transaction to insert a new data object. If the corresponding change transaction is configured to modify an existing data object or insert a new data object into the corpus, the corresponding update index message generated by the monitor and sent to the search engine, may contain an identifier of the first data object (i.e., the modified or inserted data object or the data object to be modified or inserted) or information which can be used to generate the identifier of the first data object. The update index message may include an indication that the first data object will be or was modified or inserted into the corpus, although the indication can merely indicate that a data object is being removed. Further, in situations where the corresponding transaction is one to modify or insert a new data object, the update index message generated and transmitted to the search engine may include some or all of the contents of the data object or enough information about the data object to enable the search engine to identify keywords within the data object that should be included in or removed from the search index.

An update index module may be provided to update the search index in response to the search engine receiving the update index messages mentioned above. For example, when the search engine receives an update index message that a data object has been or will be deleted, the update index module may generate an identifier for the deleted data object using information contained within the update index message, if the message does not already include the identifier for the data object. Next update index module can delete all instances of the data object identifier that are contained within entries of the search index, which are mapped to keywords. Here, it is noted that the search engine need not access the corpus of data objects in order to identify deleted data objects. In other words, the search engine need not pull information from the corpus of data objects when it is time to update a search index. Rather, the transaction monitor pushes information to the search engine that is needed to update the search index.

When the update index module message received by the search engine indicates that a data object has been or will be inserted, the update index module may generate an identifier for the inserted data object using information contained within the update index message, if the message does not already include the data object identifier. Next, the search engine or the update index module can identify keywords that are contained within the inserted data object using information that is contained within the update index message. Here, it is noted that the search engine need not access the actual, newly inserted data object in order to identify keywords contained therein. Rather, the update index message transmitted by the transaction monitor, should contain some or all of the contents of the newly inserted data object, or enough information to enable the search engine or the update index module to identify keywords of the newly inserted data object. Once the keywords are identified, the update index module may add the identifier of the newly inserted data object to each entry of the search index that contains the identified keywords. If the search index lacks one of the keywords identified in the newly inserted data object, the update index module may create a new entry in the search index, add the keyword and map the data object's identifier thereto.

When the search engine receives a message indicating that a corresponding data object has been modified, the update index module may generate an identifier for the modified data object using information contained within the message, if the message does not already include the data object identifier. The search engine or the update index module may then identify keywords contained within modified data object using information supplied in the update index message that was received from the transaction monitor. Here, again, the search engine need not access the actual, modified data object to identify the keywords contained therein. Rather, the message received by the search engine may include some or all of the data contents of the modified data object, or enough information to enable the search engine or the update index module to identify the keywords contained within the modified data object. Thereafter, the update index module may access the search index and add the identifier of the modified data object to entries of the search index that contain the identified keywords, if the entries do not already include the modified data object's identifier. If the search index does not include an identified keyword of the modified data object, the update index module may create a new entry and add this missing keyword and the modified data object's identifier mapped thereto. Lastly, the search engine may delete all instances of the modified data object's identifier in the search index that are mapped to keywords that are no longer contained within the modified data object.

The method or apparatus described herein can be used to update search indexes in which keywords are mapped to one or more data object identifiers. While the data objects can take any structured or unstructured form, the method or apparatus will be described with reference to data objects that take form in records within database tables, it being understood that the claims below should not be limited thereto. FIG. 1 illustrates in block diagram form, relevant components of a data processing system 10, which includes a memory system that stores one or more databases. The method or apparatus will be described with reference to a single database, it being understood that the claims below should not be limited thereto. Moreover, the claims below should not be limited to the system shown in FIG. 1.

System 10 includes an application program 12 executing on a computer system (not shown) such as a server. Application 12 is in data communication with a memory system 14 via communication link 16, which although not shown may include one or more software and/or hardware components such as an I/O driver, volume manager, database manager, routers, switches, etc. Memory system 14 may take form in one or more memory devices such as disk arrays. Memory system 14 stores a database, which includes one or more tables, each of which is uniquely identified by a name. Each table includes one or more records, each of which is uniquely identified by a row number. Each record contains fields or columns of data. Each record is accessible by a database manager (not shown), which are well known to those skilled in the art. For the purposes of explanation only, it will be presumed that memory system 14 contains a single database named DB, which in turn contains three tables named Table A, Table B, and Table C.

Application 12 has access to records within the database table of memory system 14 via communication link 16. More particularly, application 12 is configured to generate transactions including those for (1) deleting existing records from memory system 14, (2) inserting new records into memory system 14, or (3) modifying existing records within memory system 14. Application 12 may generate these transactions in response to receiving requests from client computer systems (not shown) in data communication therewith. As shown in FIG. 1, application 12 includes a transaction monitor 20 in data communication with a change transaction log 22, both of which will be more fully described below.

Application 12 in general and transaction monitor 20 in particular, is in data communication with a search engine 24 via communication link 26. While the method or apparatus described herein can be employed with any type of search engine, the method or apparatus will be described with reference to using an enterprise search engine, it being understood that the claims below should not be limited thereto. Search engine 24 may take form in instructions executing on a computer system (not shown) such as a server. Search engine 24 may be in data communication with other transaction monitors (not shown) executing on other computer systems that have access database records that are stored in memory system 14. These other transaction monitors could operate in a fashion similar to the operation of transaction monitor 20, which is more fully described below.

Search engine 24 includes an index update module 30, which is in data communication with transaction monitor 20 via communication link 26, which may include one or more hardware and/or software components such as drivers, switches, routers, etc. Update index module 30 is also in data communication with a memory device 36 via communication link 38, which like communication link 16, may include one or more hardware and/or software components such as file system managers, switches, etc. Memory device 36 stores a search index 32 that is related to the database DB in memory system 14, and which will be more fully described below. In general, update module 30 is configured to update search index 32 in accordance with update index messages received directly or indirectly from transaction monitor 20.

FIG. 2 graphically illustrates relevant contents of an example search index 32 that was created by search engine 24. Search index 32 includes n entries, each of which contains a keyword (e.g., keyword KW1) mapped to one or more record identifiers (e.g., RI5, RI12, and RI250) that identify respective records within the database DB of memory system 14. Search index 32 maps a keyword to a record identifier if the corresponding record contains at least one instance of the keyword. Search engines create search indexes, such as search index 32, using a process that is well understood by those of ordinary skill in the art. It is noted that search index 32 need not include every word contained within a particular record, but search index 32 should include those keywords that search engine 24 deems may be relevant to future search queries.

Search index 32 uses record identifiers (e.g., RI5) to identify records of the database in memory system 14. Record identifiers can be generated in one of many ways. However, all record identifies should be generated in the same manner and each should uniquely identify a particular record within memory system 14. For purposes of explanation only, each record identifier (e.g., RI5) of search index 32 is generated by concatenating a row number of the corresponding record and a table name (e.g., Table A, Table B, or Table C) of the table that contains the corresponding record. To illustrate, the database of memory system 14, as noted above, contains at least three tables named Table A, Table B, and Table C. Table A may include 100 records that are identified by row numbers 1-100, respectively; Table B may include 200 records that are identified by row numbers 1-200, respectively, and; Table C may include 300 records, which are identified by row numbers 1-300, respectively. The record identifier for the record in the second row of Table A may be generated as TableA:Row2; the record identifier for the record in the fifth row of Table B may be generated as TableB:Row5, and; the record identifier for the record in the eight row of Table C may be generated as TableC:Row8. It is noted, however, the foregoing is one example of record identifier structure, and the term data object identifier should not be limited to an identifier that is a concatenation of a table name and the row number of a record contained within that table.

Transaction monitor 20 monitors record changing transactions generated by application 12, including those that delete existing records, modify existing records, or insert new records into the database of memory system 14. Transaction monitor 20 generates update index messages in response to detecting the generation of transactions that change (i.e., delete, modify, or insert) records within the database. Index update module 30 can update search index 32 in accordance with the update index messages generated by and received from transaction monitor 20. Each of these messages may include information (e.g., the row number of the record that was or will be changed and the name of the table that contains the record that was or will be changed), which update module 30 can use to generate a record identifier for the corresponding record that was or will be changed. Alternatively, each of the update index messages received by update module 30 may include the record identifier of the record was or will be changed. However, for purposes of explanation only, it will be presumed that each of the update index messages that are received by update module 30, will include information (e.g., the row number of the record that was or will be changed and the name of the table that contains the record that was or will be changed), which update module 30 can use to generate a record identifier.

FIG. 3 is a flow chart illustrating relevant aspects of an example process implemented by transaction monitor 20. In response to detecting a change transaction that was generated by application 12, transaction monitor 20 accesses change transaction log 22 and creates a new entry therein as shown in step 42. In general, transaction log 22 contains one or more entries each one of which stores information regarding information about a record that was or will be changed. FIG. 4 is a graphical representation showing relevant aspects of an example transaction log 22. As seen, change transaction log 22 of FIG. 4 includes p entries, each one of which corresponds to a transaction generated by application 12 for deleting a record, modifying a record, or inserting a new record into the database DB of memory system 14. Transaction monitor 20 can create each entry before or after the corresponding record change transaction is implemented. Information added to each entry by transaction monitor 20 may be derived from the corresponding record change transaction, returned from another component (e.g., database manager) of system 10 in response to a request generated by transaction monitor 20, or a combination thereof.

Each entry within the change transaction log 22 shown in FIG. 4 includes an action type which defines the corresponding change transaction type of (i.e., delete, modify, or insert), a timestamp indicating the time when the corresponding change transaction was generated by application 12 or the time when the corresponding change transaction was completed, a table name that contains the record that is the target of the corresponding change transaction, a row number of the target record, and optionally some or all of the data contents of the record that is the subject of the corresponding change transaction or other information that can be used to identify keywords in the target record. It is noted that entries of change transaction log 22 need not include a copy of some or all of the data contents of corresponding target records. Rather, change transaction log 22 may include a pointer in each entry to a memory location where data contents of the target record can be read and copied into an update index message. Moreover, in one embodiment, change transaction log 22 need not include a copy of some or all of the data contents for a record that was or will be deleted. However, for purposes of explanation, it will be presumed that each entry of change transaction log 22 will include a copy of the data content of the record that was modified, deleted, or inserted in accordance with a corresponding change transaction.

Returning to FIG. 3 and with continued reference to FIGS. 1 and 4, transaction monitor 20 creates a new entry in the change transaction log 22 in response to receiving or detecting an application generated transaction to delete, modify, or insert a record as shown in step 42. In response, as shown in step 44, transaction monitor 20 updates the newly created entry by adding into the appropriate columns: the table name that contains the target record; the row number of the target record; the action type (i.e., D for delete record, M for modify record, or I for insert record) of the change transaction received in step 40; a timestamp TS, and; a copy of the record that was modified, deleted, or newly inserted.

In addition to creating and maintaining log 22, transaction monitor 20 is configured to generate and send update index messages to update search index 32. FIG. 5 illustrates relevant operational aspects of an example process that is implemented by transaction monitor 20 for generating and sending update messages to update module 30. In this example process, transaction monitor 20 generates and sends multiple update messages that correspond to respective entries in log 22.

The process shown in FIG. 5 begins with step 60 in which transaction monitor 20 sets a time variable t_(end) to the current time (i.e., the time when the process of FIG. 5 is initiated). In step 62, transaction monitor 20 sets a counter variable x to 0. In step 62, transaction monitor 20 increments counter x by 1. Then in step 63, transaction monitor 20 accesses entry x of transaction log 22 to read the timestamp TS contained therein. Transaction monitor 20 compares timestamp TS in entry x with t_(end) and t_(begin), where t_(begin) generally identifies the last time the process of FIG. 5 was initiated. If TS of entry x is determined to be between t_(begin) and t_(end), then transaction monitor 20, as shown in step 70, generates a new index update message. Transaction monitor 20 then adds the table name, row number and action type of entry x of log 22 to the update index message generated in step 70. If the action type of entry x is set to I or M, then some or all of the record copied to entry x is added to the message as shown in step 76. Otherwise as shown in step 80, transaction monitor 20 sends the update index message to the update module 30 via communication link 26. In step 84, x is compared to p, which represents the total number of entries contained within change transaction log 22 at the time. If x does not equal p, the process is repeated after x is incremented by 1. If x does equal p in step 84, then in step 86 the transaction monitor 20 sets t_(begin) to t_(end) and the process ends. In an alternative embodiment entries within change transaction log 22 may be deleted once they are processed in accordance with that shown in FIG. 5, in order to reduce the amount of memory needed to store change transaction log 22.

FIG. 6 illustrates relevant aspects of an example process that is performed by index update module 30 in response to receiving an index update message that was generated and sent by transaction monitor 20 in accordance with the process shown in FIG. 5. Using the process shown in FIG. 6, index update module 30 can update search index to reflect changes to the database records stored within memory system 14. In step 100, update module 30 receives an update index message from transaction monitor 20 via communication link 26. In step 102 update module 30 generates a record identifier by concatenating the table name and record row number that is contained in the received update message. In step 104, index update module 30 accesses the received update index message to determine the action type contained therein. If action type is set to D for delete, then the process proceeds to step 106 where index update module 30 removes or deletes all instances of the generated record identifier from entries of search index 32 that are mapped to keywords. Once all the instances of the generated data object identifier are deleted in accordance with step 106, the process ends.

If the action type of the received update message is not set to D for delete, then the action type is set to either I for insert or M for modify, and the received update index message should include data (e.g., a copy of some or all of the data contained in the modified or newly inserted record, or other information) that can be used by a search engine 24 to identify keywords that are contained within the corresponding modified or newly inserted record. In step 110 search engine 24 or update index module 30 processes the aforementioned data to identify keywords using the data of the received update index message. Once the keywords of the modified or newly inserted record are identified, update module 30 selects the first keyword and searches index 32 to determine whether the selected keyword is contained therein as shown in step 114. If the selected keyword is not found within search index 32, index update module 30 creates a new entry and adds the selected keyword thereto as shown in step 116. In step 120, the update module 30 adds the record identifier that was generated in step 102 to the entry that contains the selected keyword so that it is mapped thereto, if the entry does not already contain the record identifier.

All keywords that were identified in step 110 should be processed in accordance with steps 114-120. Once done, update module 30 determines whether the action type of the received update index message is set to I for insert as shown in step 124. If the action type is set to I, the process ends. If action type of the received message is set to M for modify, the process proceeds to steps 126-140 in which index update module 30 seeks to remove keywords from search index 32 that are no longer contained within the corresponding modified record. In step 126 update module 30 sets a counting variable y to zero and increments this variable in step 130. Thereafter, entry y of the search index 32 is accessed to determine whether it contains the record identifier that was generated in step 102 and whether the keyword contained within entry y is also contained within the list of keywords that were identified in step 110. In step 136, index module 30 will delete the record identifier that was generated in step 102, from entry y if the keyword of entry y is not also contained in the identified keywords of the modified record. Each entry of the search index is checked in accordance with steps 134 and 136 until all of the entries of the search index are checked.

The process shown in FIG. 5 can be initiated at regularly scheduled intervals or in response to a command received from a system administrator. Alternatively, transaction monitor 30 may generate update index messages immediately in response to receiving a record change transaction that was generated by application 12. In this embodiment, there may be no need for change transaction log 22. In other words, when transaction monitor 20 receives or detects a change record transaction, the transaction monitor generates and sends a message immediately to update module 30 without first creating an entry in log 22, wherein the message includes information needed by index update module 30 for updating search index 32 in accordance with the process shown in FIG. 6.

It is noted that the entries of transaction log 22 contain copies of records that were deleted from the database in memory system 14 or copies of the record data of the records that were deleted from the database. This data can be used to restore a record that was inadvertently deleted from the database. Specifically, the user of the data system 10 may have access to a user interface that enables the restoration of a deleted record from the database of memory system 14. Using the interface, the user can navigate to a graphical representation of the contents of the transaction log 22. Thereafter, the user can identify an entry contained within the transaction log that contains information related to an inadvertently deleted log. The entry within the transaction log 22 should contain all information that is necessary to store the inadvertently deleted record. Once the transaction log entry is identified, the user can initiate a restore operation in which, for example, transaction monitor 20 accesses the entry of transaction log 22 that contains the inadvertently deleted record. Information that is used to restore the inadvertently deleted log should include a copy of the record contained within the entry of transaction log 22, or the data of the inadvertently deleted record that is contained within the entry of transaction log 22, the row or record number of the inadvertently deleted record, and the table name of the table that contained the inadvertently deleted record. This information is used by transaction monitor 20 or another process implemented on server 12, to restore the record within the database of memory system 14 before it was inadvertently deleted. In addition to restoring the inadvertently deleted record, transaction monitor 12 may generate an update message that subsequently transmits to index update module 30. This update message should include the name of the table into which the inadvertently deleted record is restored, the record or row number of the inadvertently deleted record, and an indication that the record is being inserted. Index update module 30, in response to receiving this update index message, updates a search index 32 in accordance with the process shown in FIG. 6. It is noted that the update index message submitted to the index update module 30, includes a copy of the record contained within the entry of the change transaction log 22 or other information needed to update the search index 32 in accordance with the process shown in FIG. 6.

Transaction log 22 can be used as a clipboard or temporary memory when copying records between first and second related or unrelated database tables, or when deleting a record from the first table and subsequently pasting or inserting the record into the second related or unrelated table. Using transaction log 22 as a clipboard will enable a user to copy a record between first and second related or unrelated tables, or delete a record from the first table and insert it into the second related or unrelated table, using interfaces of separate applications executing on, for example, server 12. It is noted that transaction monitor 20 may be capable of monitoring record change transactions, including those for copying records to transaction log 22, generated by different applications executing on server 12.

A first application executing on server 12 may provide a first user interface through which a user may initiate a transaction to delete or copy a record contained within a first table of the database of memory system 14. Transaction monitor 20 may create a new entry in transaction log 22 in response to detecting this delete or copy transaction. Thereafter, transaction monitor 20 could update the newly created entry by adding a copy of the record. The transaction monitor 20 could then add the name of the first table to the newly created entry, and the transaction monitor 20 could add the row or record number of the record that was copied to the newly created entry. If the detected transaction is one to delete the record from the first table, transaction monitor 20 could update the newly created entry by identifying the action type therein as a D for delete. If the detected transaction is one to copy the record, transaction monitor 20 could update the newly created entry by identifying the action type therein as a C for copy.

After the record is copied to the transaction log 22 in response to the delete transaction, transaction monitor 20 may send an update index transaction to index update module 30 in accordance with the process shown in FIG. 5. Index update module 30 in response may update the search index 32 in accordance with process shown in FIG. 6. If the record is copied to transaction log 22 in response to a copy transaction, transaction monitor 20 need not send an update index message to index module 30 since the first table maintains a copy of the record that was copied to transaction log 22 in response to the copy transaction.

Since transaction log 22 contains the record (or the data contents thereof) that was deleted or copied from the first table, another and/or different type of application (i.e., a second application) executing, for example, on application 12 may provide a second user interface that enables its user to copy the record from the transaction log 22 to a second table. Specifically, a user of the second application may be provided a second user interface that provides access to the contents of the change transaction log 22 to allow the user to view the contents thereof. In one embodiment, the second interface may provide a list that identifies the records that are contained in transaction log 22. The list may identify the records by table name and row or record number. This second interface may allow the user to designate record identified in the list. The second interface may also enable the user to initiate a transaction to copy a record from transaction log 22 to a second database table. Specifically, when a record is designated by the user, transaction monitor 20 can copy the designated record from transaction log 22 to the second table in response to transaction monitor 20 receiving a copy instruction from the second application that identifies the user designated record, the identification of the second table, and a command to copy. Thereafter, transaction monitor 20 may generate an update index message that indicates that a new record has been inserted into the second table. This update index message may include the name of the second table, the row number of the second table where the record was copied, an action type set to I for insert, and a copy of the record or enough information to enable index update module to update search index 32. This update index message will be sent to index update module 30, which in turn updates search index 32 in accordance with the process shown in FIG. 6.

Although the invention has been described in connection with several embodiments, the invention is not intended to be limited to the specific forms set forth herein. On the contrary, it is intended to cover such alternatives, modifications, and equivalents as can be reasonably included within the scope of the invention as defined by the appended claims. 

1. A method comprising: a first application generating a transaction for deleting a record from a first table in a database; deleting the record from the first table; in response to the generation of the first transaction, storing a copy of the record in an entry of a transaction log before the record is deleted from the first table; a second application generating an instruction for copying the record from the transaction log to a second table; copying the record from the entry to the second table.
 2. The method of claim 1 wherein the first and second applications are distinct.
 3. The method of claim 1 further comprising: generating a first message in response to generating the transaction, wherein the first message comprises a table name of the first table and an identifier of the record in the first table, and wherein the first message comprises information that indicates that the record was or will be deleted; transmitting the first message to a computer system that implements a search engine.
 4. The method of claim 3 wherein the search engine generates a first index identifier of the record using the first table name and the identifier of the record in the first table.
 5. The method of claim 4 further comprising removing all instances of the first index identifier from a search index.
 6. The method of claim 1 further comprising: generating a second message in response to generating the instruction, wherein the second message comprises the table name of the second table and the identifier of the record in the second table, and wherein the second message comprises information that indicates that the record has been inserted into the second table; transmitting the second message to the computer system that implements the search engine.
 7. The method of claim 6 wherein the search engine generates a second index identifier of the record using the second table name and the identifier of the record in the second table.
 8. The method of claim 4 further comprising adding at least one instance of the second index identifier to the search index.
 9. A method comprising: a first application generating a first instruction for copying a record from a first table in a database to an entry of a transaction log; in response to the generation of the first instruction, copying the record from the first table to the entry; a second application generating a second instruction for copying the record from the transaction log to a second table; copying the record from the entry to the second table.
 10. The method of claim 9 wherein the first and second applications are distinct.
 11. The method of claim 9 further comprising: generating a message in response to generating the second instruction, wherein the message comprises a table name of the second table and an identifier of the record in the second table, and wherein the message comprises information that indicates that the record was inserted into the second table; transmitting the message to a computer system that implements a search engine.
 12. The method of claim 11 wherein the search engine generates an index identifier of the record using the second table name and the identifier of the record in the second table.
 13. The method of claim 12 further comprising adding at least one instance of the index identifier to a search index.
 14. A computer readable medium (CRM) storing instructions, wherein a method is implemented in response to executing the instructions, the method comprising: receiving a first instruction for deleting a record from a first table in a database, wherein the first instruction is received from a first application; deleting the record from the first table; storing a copy of the record in an entry of a transaction log before the record is deleted from the first table; receiving a second instruction for copying the record from the transaction log to a second table, wherein the second instruction is received from a second application; copying the record from the entry to the second table.
 15. The CRM of claim 14 wherein the first and second applications are distinct.
 16. The CRM of claim 14 wherein the method further comprises: generating a first message in response to receiving the first instruction, wherein the first message comprises a table name of the first table and an identifier of the record in the first table, and wherein the first message comprises information that indicates that the record was or will be deleted; transmitting the first message to a computer system that implements a search engine.
 17. The CRM of claim 16 wherein the method further comprises generating a second message in response to receiving the second instruction, wherein the second message comprises the table name of the second table and the identifier of the record in the second table, and wherein the second message comprises information that indicates that the record has been inserted into the second table; transmitting the second message to the computer system that implements the search engine. 